-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Rearrange into logical sections and add relevant links #9639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- When writing tests, use 2.6 compatible `self.assertFoo` methods. Some polyfills such as `assertRaises` | ||
can be found in `pandas.util.testing`. | ||
- Do not attach doctrings to tests. Make the test itself readable and use comments if needed. | ||
- **Make sure the test suite passes** on your box, use the provided `test_*.sh` scripts or tox. Pandas tests a variety of platforms and Python versions so be cognizant of cross-platorm considerations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably mention Travis-CI here, and the ease of setting up Travis on your own fork.
This looks like a nice improvement! Merging... |
Rearrange into logical sections and add relevant links
- Optionally, a commit message body. | ||
- Please reference relevant Github issues in your commit message using `GH1234` | ||
or `#1234`. Either style is fine but the '#' style generates noise when your rebase your PR. | ||
- `doc/source/vx.y.z.txt` contains an ongoing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now doc/source/whatsnew/vx.y.z.txt
@rockg Thanks a lot for this! Just a comment about the numpydoc reference, but maybe I missed it. |
It is at the top of the "Documentation / Commit Messages" section (I felt it was important). |
Ah, so I missed it! :-) |
This rearranges the Contributing page into more logical sections and provides some more useful links to wiki pages. I think this should be the place where all relevant documentation on pandas development can be found. For example, both this page and the pandas homepage mention
vbench
but the information on running tests was lacking and it turns out that the wiki has this information but it was difficult to find. Hopefully this is a step in the right direction.